Redmine Contracts

info

For more information on Redmine usage, refer to 262COS-COMM-AID-002 - Redmine Operation will be found in /04_COMMUNICATION/AID-002%20-%20Redmine%20Operation/00_introduction.

Contract (Event)	Authority (Initiator)	Communication (Message)	Action (Message-Response)
Tactical Objective Creation	ME Lead (MEL)	Project: `Mission` Tracker: `Objective` Subject: `TO-#: [Tactical objective title]` Start date: Mission start date Due date: Mission end date Assignee: The ME Lead (MEL) Description: `[Measure of effective for the tactical objective]`	ME Lead (MEL): Throughout the lifecycle of the objective, annotate notes and change the issue status to `In Progress`, `Blocked`, `Complete`, or `Abandonded` when appropriate
Tactical Task Creation	ME Lead (MEL)	Project: `Mission` Tracker: `Task` Subject: `TT-#.#: [Tactical task title]` Start date: Mission start date Due date: Mission end date Assignee: Crew member responsible for the task Description: `[Measure of performance for the tactical task]`	ME Lead (MEL): After creation, link the `Task` issue to the parent `Objective` issue Assignee: Throughout the lifecycle of the task, annotate notes and change the issue status to `In Progress`, `Completed`, `Blocked`, or `Abandonded` when appropriate
Incident Escalation	Anyone	Project: `Investigations` Tracker: `Incident` Subject: `[Short unique summary of the incident]` Activity: `[Select the relevant activity description]` Assignee: Crew member responsible for the investigation Description: `[Full description of the incident]`	Author: After creation, populate IOCs in the `Indicators` table and relevant links in the `Investigation Links` table Assignee: Throughout the lifecycle of the investigation, annotate notes and change the issue status to `In Progress`, `Resolved`, `Blocked`, or `Abandonded` when appropriate
Incident Response Clear Action	Anyone	Project: `Investigations` Tracker: `Task` Subject: `[Short unique summary of the desired action]` Assignee: Crew member responsible for the task Description: `[Specific details for performing the clear action]`	Author: After creation, link the `Task` issue to the related `Incident` issue Assignee: Throughout the lifecycle of the task, annotate notes and change the issue status to `In Progress`, `Completed`, `Blocked`, or `Abandonded` when appropriate
Intel RFI/FFIR	Anyone	Project: `Intel` Tracker: `Request` Subject: `[Short unique summary of the RFI/FFIR]` Assignee: Intel analyst responsible for the request Description: `[Specific information request details]`	Assignee: Throughout the lifecycle of the request, annotate notes and change the issue status to `In Progress`, `Feedback`, `Blocked`, `Rejected`, `Complete`, or `Abandonded` when appropriate
W/S Support Request	Anyone	Project: `W/S Support` Tracker: `Request` Subject: `[Short unique summary of the support request]` Assignee: Crew member responsible for the request Description: `[Specific support request details]`	Assignee: Throughout the lifecycle of the request, annotate notes and change the issue status to `In Progress`, `Feedback`, `Blocked`, `Rejected`, `Complete`, or `Abandonded` when appropriate
Notice to the team	Anyone	Project: Whichever relevant project Tracker: `Request` Subject: `[Short unique summary of the notice]` Assignee: `Everyone` Description: `[Specific notice details]`	Author: When the notice is no longer relevant, change the issue status to `Closed`